Make the lib fully strict typed - #136

Model optional Fritzhome state and guard remote operations

pyfritzhome/​devicetypes/​fritzhomeentitybase.py:21

_fritz is actually None whenever the public constructor is called without fritz, but this cast tells strict mypy it is always a valid Fritzhome. Subclass methods then dereference it without checks, so the newly published typing hides a real runtime state instead of modeling it. Please make _fritz optional and guard those methods, or require a Fritzhome for objects that expose remote operations.

Reject empty login challenges

pyfritzhome/​fritzhome.py:245

An empty <Challenge/> is also unusable but is not caught by this None check; it falls through to the MD5 path and sends a response derived from an empty challenge instead of reporting the malformed login response. Reject empty strings as well.

Ensure getter colors are non-optional and setter-compatible

pyfritzhome/​fritzhome.py:500

This return type is incompatible with the documented set_color() workflow: get_colors() produces Sequence[str | None], while set_color() accepts only Sequence[str | SupportsInt]. Strictly typed clients therefore cannot pass a returned color to the setter, and widening the setter would be unsafe because it calls int() on the values. Validate/filter missing XML attributes and expose non-optional color tuples in both public layers.

Normalize missing color temperatures before exposing them

pyfritzhome/​fritzhome.py:540

get_color_temps() now returns list[str | None], but set_color_temp() rejects None, so a value obtained from the getter cannot be passed to the setter under strict typing. Since the setter also executes int(temperature), normalize or reject missing value attributes here and publish list[str] consistently through the device wrapper.